Event Descriptions

 
The event log contains a list of events which have occurred in a device. Descriptions of the events are detailed below.

0 Unknown event

• Fault

• Unknown events

An event occurred which HiQnet London Architect does not know about.

1 CError

• Fault

• Unknown events

Description

An internal error occurred. There is no user-friendly description, but the error numbers can be used by BSS to try and trace any problems.

5 IP Address Change

• Info

• Network events

• Example Details :- IP address has changed 192.168.0.1

Description

The IP address of the device was changed. This change would be caused by DHCP, Auto IP or the user allocating a fixed address.

6 Device booted

• Warning

• Miscellaneous events

• Example Details :- The device has booted, version:1.14.0

Description

The device was powered up. If you see these events at unexpected times then it indicates problems with the power supply to the device.

9 Conductor status changed

• Info

• CobraNet events

• Example Details :- On

Description

The CobraNet conductor status changed.

11 Mute changed

• Info

• CobraNet events

• Example Details :- Mute

Description

The CobraNet mute status has changed.

12 Activated venue preset

• Info

• Configuration events

• Example Details :- 1

Description

A venue preset was activated. This will be due to the device being loaded or the device acting upon a venue recall.

13 Activated parameter preset

• Info

• Configuration events

• Example Details :- 1

Description

A parameter preset was activated. This will be due to the device acting upon a parameter preset recall.

14 Failed to activate venue preset

• Fault

• Configuration events

• Example Details :- 1

Description

A venue preset failed to activate. Typically, the configuration files are missing or corrupt due to a failed load of the device.

15 Failed to activate parameter preset

• Fault

• Configuration events

• Example Details :- 1

Description

A parameter preset failed to activate. Typically, the configuration files are missing or corrupt due to a failed load of the device.

16 TX bundle changed

• Info

• CobraNet events

• Example Details :- CobraNet transmit bundle was setBundle A transmitting on 1000

Description

An output bundle changed the bundle number it is transmitting on.

17 RX bundle changed

• Info

• CobraNet events

• Example Details :- CobraNet receive bundle was set Bundle B receiving on 1001

Description

An input bundle changed the bundle number it is receiving on.

18 DSPs reset

• Info

• DSP events

Description

The DSPs were reset. This is quite normal and will happen every time a configuration is loaded.

19 Audio on

• Info

• DSP events

Description

The audio was turned on. The audio is turned back on as the last step of a configuration change.

20 Audio off

• Info

• DSP events

Description

The audio was turned off. The audio is turned off as the first step of a configuration change.

21 DSPs crashed

• Fault

• DSP events

Description

The DSPs crashed and were restarted.

22 DSPs recovered after crash

• Info

• DSP events

Description

The DSPs successfully restarted after a crash.

23 Wrong CM1 firmware

• Fault

• Configuration events

• Example Details :- Incorrect CM1 firmware for required sample rate.  

Description

The firmware of the CM1 CobraNet card needs to be updated to support the sample rate of the design being loaded.

34 Failed to recall venue

• Fault

• Configuration events

• Example Details :- Failed to recall a venue configVenue attempted 1

Description

A HiQnet venue recall failed.

35 Failed to recall scene

• Fault

• Configuration events

• Example Details :- Failed to recall a scene parameter Scene attempted 2

Description

A HiQnet scene recall failed.

36 Failed to load config files

• Fault

• Configuration events

• Example Details :- Failed to load the config files for the unit Error code 0

Description

The configuration files failed to load. Typically this is caused by corrupt files due to a failed ftp session.

37 Device has gone offline

• Warning

• Application events

• Example Details :- Device name

Description

One of the devices on the network stopped communicating to HiQnet London Architect.

38 Device has come online

• Info

• Application events

• Example Details :- Device name

Description

A device on the network started communicating to HiQnet London Architect.

39 Device has lost connection

• Warning

• Application events

• Example Details :- Device name

Description

One of the devices on the network was not responding as quick as expected or was responding intermittently.

40 Device has gained connection

• Info

• Application events

• Example Details :- Device name

Description

A device on the network started responding correctly after 39 "Device has lost connection"

41 Going online

• Info

• Application events

Description

Simply a record of when HiQnet London Architect went online.

42 Going offline

• Info

• Application events

Description

Simply a record of when HiQnet London Architect went offline.

43 Attributes never returned from device

• Fault

• Application events

Description

HiQnet London Architect was unable to fully discover a device on the network.

44 Synchronisation to device failed

• Fault

• Application events

• Example Details :- Device name

Description

The user has chosen to have HiQnet London Architect to automatically re-synchronize offline devices in the file preferences. However, HiQnet London Architect failed to synchronize a device.

45 New failed

• Fault

• Memory events

Description

The device ran out of memory. This would usually indicate a software error, but could also be caused by a very large design.

46 Device failed to load configuration within timeout

• Fault

• Application events

• Example Details :- Device name

Description

HiQnet London Architect tried to load a device, but timed-out because the device took too long to load the configuration.

47 No network sockets

• Info

• Network events

 
Description

The device ran out of TCP sockets. TCP sockets are used to communicate with devices, and are used for FTP, Telnet and HiQnet. There is a finite number of sockets, and once they are all open, no more will be available until one has been closed.

48 Fatal Error

• Fault

• Miscellaneous events

Description

A serious error occurred on the device and it had to be rebooted. Details of the error should be sent to BSS Audio to help resolve the problem.

49 Packet could not be sent

• Warning

• Network events

• Example Details :- Destination node 0x100

Description

A HiQnet message could not be sent. This would usually be because the destination device is not present on the network.

50 Keep alive failed

• Warning

• Network events

• Example Details :- Node 0x100

Description

The HiQnet route to a device timed out. This will occur normally when new devices are powered up and announce themselves to the network. However, if this occurs between two devices that should have a permanent connection (e.g. Because of linking etc) then this would indicate a problem.

51 Serial receive buffer high tide

• Warning

• AMX/Serial events

• Example Details :- The serial input buffer reached 80% full

Description

The RS232 input buffer was getting full. This would indicate that too much serial data was being set to the device.

52 Serial receive buffer full

• Fault

• AMX/Serial events

• Example Details :- The serial buffer was completely full and characters will be lost

Description

The RS232 input buffer was full and characters were probably lost. This would indicate that too much serial data was being set to the device.

53 Ethernet receiver frame length error

• Fault

• Network events

• Example Details :- The last ethernet frame was too long

Description

An Ethernet packet was received which was too long. This indicates a possible problem with the network.

54 Ethernet receiver data not aligned

• Fault

• Network events

• Example Details :- A frame contained a number of bits not divisible by 8

Description

An Ethernet packet was corrupt. This indicates a possible problem with the network.

55 Ethernet received a short frame

• Fault

• Network events

• Example Details :- The last ethernet frame was too short

Description

An Ethernet packet was corrupt. This indicates a possible problem with the network.

56 Ethernet receiver CRC error

• Fault

• Network events

• Example Details :- The last ethernet frame contains a CRC error

Description

An Ethernet packet was corrupt. This indicates a possible problem with the network.

57 Ethernet receiver buffer overrun

• Fault

• Network events

• Example Details :- A receiver FIFO overrun occurred, possibly due to packet storm 2000 buffers used

Description

The device ran out of Ethernet packets. This is usually due to a packet storm created when a network contains a loop.

58 Ethernet receiver buffer truncated

• Fault

• Network events

• Example Details :- The receiver truncated the frame, most likely because it was too long

Description

An Ethernet packet was corrupt. This indicates a possible problem with the network.

59 Failed to discover device

• Warning

• Network events

• Example Details :- Node 0x200

Description

The device failed to discover another device on the network. Check that the device it is looking for is running and connected to the network correctly.

60 TCP stream invalid

• Warning

• Network events

• Example Details :- IP=192.168.0.2

Description

A HiQnet socket has become corrupt. This would indicate a problem with the network or the device with the IP address shown in the details.

61 Packet store empty

• Warning

• Network events

Description

The device ran out of HiQnet packets which it uses internally. This would indicate that it is having trouble sending out packets and that many of them are being queued up.

62 TCP send failed

• Warning

• Network events

• Example Details :- Node 0x42

Description

The device failed to send some data on a socket to the device with the HiQnet node address shown in the details.

63 Cobranet firmware reprogram failed

• Fault

• Cobranet events

• Example Details: Something went wrong in reprogramming the CM1 module.

Description

An error occurred whilst reprogramming the CM1 flash. The numbers given in the details are error numbers.

64 Digital input card error status change

• Warning

• Digital I/O events

• Example Details :- Digital input card error status changed Card :3 Channels 1&4 To value Error cleared

Description

These events are included to help monitor the digital audio cards.

65 Digital input card non audio status change

• Warning

• Digital I/O events

• Example Details :- Digital Digital input card non-audio status changed Card:3 Channels1&2 To value Non audio cleared

Description

These events are included to help monitor the digital audio cards.

66 Digital input card marginal status change

• Warning

• Digital I/O events

• Example Details :- Digital input card marginal status changed Card3 Channels3&4 To value Marginal

Description

These events are included to help monitor the digital audio cards.

67 Digital input card Receiver lock change

• Warning

• Digital I/O events

• Example Details :- Digital input card receiver lock status changed Card2 Channels1&2 To value: Locked

Description

These events are included to help monitor the digital audio cards.

68 Digital input card SRC lock error

• Fault

• Digital I/O events

• Example Details :- Digital input card sample rate converter lock error Card3 Channels3&4 To value Lock recovered

Description

These events are included to help monitor the digital audio cards.

69 Digital input card Bypass change

• Info

• Digital I/O events

• Example Details :- Digital input card bypass setting changed Card0 Channels1&2 To value Bypass

Description

These events are included to help monitor the digital audio cards.

70 Digital input card SyncBus drive change

• Info

• Digital I/O events

• Example Details :- Digital input card Syncbus setting changed Card1 To value channel A

Description

These events are included to help monitor the digital audio cards.

71 Digital input card Type change

• Info

• Digital I/O events

• Example Details :- Digital input card Type setting changed Card3 Channels1&2 Type SPDIF

Description

These events are included to help monitor the digital audio cards. The type can be either AES or SPDIF.

72 Digital output card Type change

• Info

• Digital I/O events

• Example Details :- Digital output card Type setting changed Card2 Channels1&2 Type AES

Description

These events are included to help monitor the digital audio cards. The type can be either AES or SPDIF.

73 Digital output card Bypass change

• Info

• Digital I/O events

• Example Details :- Digital output card bypass setting changed Card3 Channels3&4 To value Not bypass

Description

These events are included to help monitor the digital audio cards.

74 Digital output card SyncBus drive change

• Info

• Digital I/O events

• Example Details :- Digital output card Syncbus setting changed Card: 2 To value: channel B

Description

These events are included to help monitor the digital audio cards.

75 Digital output card Status change

• Info

• Digital I/O events

• Example Details :- Digital output card Status changed Card3 Channels3&4 Value Error: circular sync

Description

These events are included to help monitor the digital audio cards.

• The value can be:-

• • locked

  • not locked

  • Error: sync to self

  • Error: sync to analogue card

  • Error: sync to empty slot

  • Warning: incompatible clock

  • Error: circular sync

  • Error: unknown status value

76 DHCP lease expired

• Warning

• Network events

• Example Details :- The IP address assigned by DHCP has expired 192.168.1.2

Description

The IP address timed out and the device reverted back to auto IP. This would indicate that the DHCP server on the network has stopped working or the device can no longer communicate with the DHCP server.